merge isName and isNameInsensitive#1896
Merged
TomasVotruba merged 1 commit intomasterfrom Aug 25, 2019
Merged
Conversation
TomasVotruba
force-pushed
the
sensitive
branch
from
f42f248 to
f0d5b5a
Compare
TomasVotruba
added a commit
that referenced
this pull request
Mar 3, 2022
rectorphp/rector-src@85e39c7 [Privatization] Allow only current class const fetch to avoid unnecessary assign constant to constant (#1896)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When working with legacy code, from technical point of view all names are insesntive:
is the same as:
Saying that, all
*Name*methods work will match both names